-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Update the next tag when a alpha/beta release is published #12096
Conversation
|
Isn't If they're migrating from the alpha to the beta, I think it's important for them to opt-in to the beta with |
|
Perhaps we could redirect I guess my proposal is:
I think it's valuable still to hide |
|
@bluwy The We shouldn't overload the meaning of ref to mean npm tags instead. Git refs and npm tags are different things. npm tags don't have any actual meaning to them. They are just pointers to a version. You can name them anything you want, it doesn't matter that I can see there being slight confusion about passing |
I get how ref and npm tags work. My point is that it feels like we're mixing them up. When we announce the alpha or the beta, users shouldn't encounter another term
Checking the code, I think astro/packages/create-astro/src/actions/template.ts Lines 74 to 82 in e748c48
We can setup the same way we sync the astro/.github/workflows/main.yml Lines 63 to 77 in e748c48
I think we already have pkg.pr.new to handle that Taking a step back, I think my proposal is indeed kinda wild. But I do like the idea of syncing the But also like most of my comments, I don't think it's the end of the world if we want to go with this PR. I was thinking it's worth reducing the confusion a bit. |
I do agree that using the term |
Closing since it seems like we won't do this. Not sure how fun it'd be to migrate from |
Changes
This makes it so
astro@next
always point to the latest release of thenext
branch. This makes it a bit more easier for users to update between alphas to beta etc as they can always justnpm install astro@next
. In the future, this could also power nightly or canaries versions perhaps.Right now this only updates
astro
, it could be extended to support every integration if we deem it necessaryTesting
It won't work, it's GitHub Actions
Docs
N/A